relationships entries should bind to a service endpoint (string form), not an empty mapping. The canonical structure in references/config.md uses e.g. relationships: database: 'db:postgresql' (config.md:64). Update this example to bind db to the db service endpoint.

The deploy hook hard-codes default admin credentials (admin@example.com / password). Even if this is “first deploy only”, it’s an insecure default that can be accidentally exposed. Prefer generating a random password, requiring explicit env vars, or documenting a manual bootstrap step instead of committing defaults.

relationships entries should bind to a service endpoint (string form), not an empty mapping. The canonical structure in references/config.md uses e.g. relationships: database: 'db:postgresql' (config.md:64). Update this example to use the correct relationship binding for db and redis.

The .environment file is written with unquoted heredoc (<< EOF), so $PLATFORM_PROJECT_ENTROPY will be expanded immediately and any relationship vars (if added later) would be empty because build hooks have no service env. Also, these assignments aren’t exported, so they won’t reach the npm start process. Use a quoted heredoc and export … lines (or append export statements via echo 'export …' >> .environment).

relationships entries should bind to a service endpoint (string form), not an empty mapping. The canonical structure in references/config.md uses e.g. relationships: database: 'db:postgresql' (config.md:64). Update this example to bind database to the database service endpoint.

This PHP app example doesn’t set build.flavor: none, which conflicts with the PHP guidance in references/php.md (and other PHP framework references) and can lead to implicit Composer behavior or duplicated installs. Add build: { flavor: none } to keep dependency management explicit.

The “standard runtime image” example also runs npm run build without first installing dependencies. Add npm ci/npm install (or the detected package manager) before the build command so the example is runnable.

npm ci --omit=dev will typically remove the devDependencies that Vite needs to run the build (Vite is usually in devDependencies). This makes npm run build fail for most Vite projects. Install dev deps for the build (e.g. npm ci) and, if needed, prune afterwards (or rely on a static runtime with no node_modules at runtime).

The “YAML example” blocks here don’t match Upsun’s .upsun/config.yaml schema (they use runtime/build/static keys rather than applications/web/locations). This will mislead users/agents. Rework the examples to use the standard Upsun structure shown in references/config.md (applications + build hook + web.locations serving dist/ or build/ with SPA passthru).

Same issue as earlier in the file: relationships: db: {} is not a valid binding in Upsun configs. Use the string binding form shown in references/config.md (config.md:64), e.g. db: 'db:postgresql' / db: 'db:mysql' depending on the service endpoint.